WCF Web Services Error

I'm getting the error "Could not find default endpoint element that references contract ' Metastorm.Runtime.Models.MyProject.WCF.MySvcWS.MyInterface' in the ServiceModel client configuration section.

This happens anytime I try to use the service. It is a valid service that I can successfully access from a regular c# project on the same system.

I am using version 9 with the latest service pack SR1 and hotfix, on Windows 2008 R2.

Any thoughts from the group?

Find more posts tagged with

BPM

Comments

Prashant Tiwari

We do not get this error any more, We created a .NET dll which included references to WCF libraries. This .NET wrapper in turn calls the WCF service. We can include this .NET dll inside Metastorm environment and call the dll method from Metastorm server script.

Henrik Persson

Hi!

I also get the " Could not find default enpoint..." when trying to call a WCF web service from a serverside script.

I also got this problem when testing the web service in a vs2008 project using a test program calling a .NET dll where

the WS calling code was implemented. The sollution in that case was to put the Ws configuration setting into the main

projects app.config file ( http://stackoverflow.com/questions/352654/could-not-find-default-endpoint-element )

Should it not be possible to call a WCF service from a server side script?

I tried to follow the HelloWorld example from Ethan in the thread V9 - How to access web methods from within a server side C# script but that resulted in the fault.

Calling the WS directly works fine but then I got problem when error occurs and exceptions are thrown, an that was what I tried to solve by calling the WS from the server script using try catch.

I guess that I'll end up using the .NET dll sollution.

Edit

I got the WS call to work now after a lot of trial and error. I did not really understand at first how to call the connectoin from the C# server side script, the syntax was much easier than I thougt.

But I did not get my .NET dll solution to work though... still got the "Could not find the endpoint.." error.

Regards

/Henrik

Aaron Van

I would have loved to hear how this was resolved.

I am receiving this error:

Details:Failed to execute deployed method 'WhenActionCompleted', using entity 'UserAction3'. Could not find endpoint element with name 'Metastorm.Runtime.Models.PulseLibrary.WCF.MyService.IMyService' and contract 'Metastorm.Runtime.Models.PulseLibrary.WCF.MyService.IMyService' in the ServiceModel client configuration section. This might be because no configuration file was found for your application, or because no endpoint element matching this name could be found in the client element.

...when I try to make a web service call from a server side script that looks like this:

Metastorm.Runtime.Models.MetaLibrary.Services.SetStage(25,
Metastorm.Runtime.Models.MetaLibrary.WCF.MyService.SomeEnum.ID,
Metastorm.Runtime.Models.MetaLibrary.WCF.MyService.OtherEnum.OtherID);

This server side script method works fine from within a visual script.

Any takers?

Michael_Turek

Do you have the methods checked in your connection's method & parameter section (connection part of the metastorm inventory)? I check the side that "promotes to the Activity toolbox". But I use it in a server script by using the name of the connection you created for that service - the metastorm connection name...

So, instead of "Metastorm.Runtime.Models.MetaLibrary.WCF.MyService"

Try using the name of your connection to your service which looks to be "MyService"

Aaron Van

Thanks for the response Mike. My methods were exposed to the expression builder and activities toolbox.

It turns out that it was just another random bug in how the web service is loaded in the designer.

All my code was correct, the fix was to remove the connection from the library all together (not just updating the service) and re-add it.

So give that a try if you run into this issue future person, you may save yourself 4 hours debugging endpoint and contract names.

Tony Lam

I get this error all the time and it normally comes down to a couple of things.

a. Caching. Even though I updated the web service connection, metastorm doesn't seem to acknowledge the changes and I would need to: Delete the web service connection, save project and close, stop metastorm services, clear cache, restart metastorm services, open project and create a new web service connection. (Seems a bit redundant but.... seems to work for me)

b. The app configuration data that metastorm build for the web service connection needs to be tweak. ("Advanced") tab of the connection object. I normally look for the and change it to "None" .

I have also used the DLL wrapper method and that works fine but has since moved away from DLL due to memory leakage and performance issues.

Regards,

Tony